TrustRadius Insights
Bitbucket Server, formerly known as Stash, is an essential tool for development teams seeking to streamline their coding cycle in a …
Overview
What is Bitbucket Server (discontinued)?
Bitbucket Server (formerly Stash) from Atlassian offered a self-hosted source code management solution. The product is no longer available for sale, and support for existing licenses will end in 2024.
Recent Reviews
Pricing
N/A
Unavailable
What is Bitbucket Server (discontinued)?
Bitbucket Server (formerly Stash) from Atlassian offered a self-hosted source code management solution. The product is no longer available for sale, and support for existing licenses will end in 2024.
Entry-level set up fee?
- No setup fee
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting/Integration Services
Would you like us to let the vendor know that you want pricing?
2 people also want pricing
Alternatives Pricing
What is Bitbucket?
Bitbucket from Australian-headquartered Atlassian offers source code management and version control.
What is GitLab?
GitLab DevSecOps platform enables software innovation by aiming to empower development, security, and operations teams to build better software, faster. With GitLab, teams can create, deliver, and manage code quickly and continuously instead of managing disparate tools and scripts. GitLab helps…
Product Details
- About
- Tech Details
What is Bitbucket Server (discontinued)?
Bitbucket Server (discontinued) Technical Details
| Operating Systems | Unspecified |
|---|---|
| Mobile Application | No |
Comparisons
Compare with
Reviews and Ratings
(28)
Community Insights
TrustRadius Insights are summaries of user sentiment data from TrustRadius reviews and, when necessary, 3rd-party data sources. Have feedback on this content? Let us know!
- Business Problems Solved
- Pros
- Cons
Bitbucket Server, formerly known as Stash, is an essential tool for development teams seeking to streamline their coding cycle in a collaborative environment. It allows teams to take control of their projects and organize a portfolio of different products. Users find it easy to deploy and manage, whether on internal or managed infrastructure, on-premises or in the cloud. This provides peace of mind and equips developers with the necessary tools for development.
One of the key use cases for Bitbucket Server is version control within teams. It facilitates collaboration among cross-functional teams located in different time zones, ensuring everyone works on the same codebase. Development teams push their code to the Stash server, which undergoes review by the testing team before final approval. Upon approval, release engineering teams pull the code from the server and move it across various environments.
Stash seamlessly handles pull requests from JIRA issues into development and production branches, making it easy for teams to merge changes into the main codebase. It even supports builds for Java applications upon acceptance of a pull request into the development branch, further streamlining the development process. With its user-friendly UI and integration with JIRA, developers can effortlessly host code repositories, create and manage pull requests, and browse individual files and commits. Bitbucket Server serves as the primary version control system in many organizations, trusted by both operations and development teams.
Moreover, Bitbucket Server offers a centralized platform that improves collaboration among multiple teams and instills confidence in IT among internal clients. Each department retains control over specific sections of code repositories, ensuring clarity and ownership. The pull request process in Stash requires two approvers for every merge, ensuring code quality and minimizing errors.
Lastly, Bitbucket Server integrates seamlessly with other Atlassian products like Bamboo, JIRA, and Confluence for a streamlined continuous delivery and continuous integration CD/CI process. This integration enables development teams to work offline, commit changes, and collaborate effectively through pull requests. Bitbucket Server's versatility makes it the preferred solution for organizations facing limitations with other systems, such as branching issues.
Intuitive and User-Friendly Interface: Reviewers have consistently praised the product's intuitive and user-friendly interface, with many stating that it is easy to navigate and perform tasks quickly. This sentiment was shared by a majority of users. Easy Deployment and Platform Management: Users appreciated the product for its easy deployment process and efficient platform management capabilities. It provides a collaborative framework for the development cycle, which has been positively acknowledged by numerous reviewers. Seamless Integration with DevOps and ITSM Tools: The ability to integrate the product with different DevOps and ITSM tools has been highly valued by users. This feature allows for seamless workflow integration, as mentioned by several customers in their reviews.
-
Restricted centralized user management: Some users have expressed dissatisfaction with Bitbucket Server's limitations on centralized user management, stating that it is not ideal for their needs. They feel that the platform should offer more flexibility in managing user permissions and access.
-
Confusing technical issue resolution: Several reviewers have found it challenging to solve technical issues that arise from time to time, leading to confusion and frustration during troubleshooting. They would appreciate clearer documentation or better guidance within the platform to help them resolve these issues effectively.
-
Lack of direct folder download in Stash: Users have suggested that Stash should allow direct download of entire folders instead of having to navigate inside each folder to download individual files, as this would improve efficiency and ease of use. This feature enhancement would save users time and effort when they need to download multiple files located within the same folder structure.
Attribute Ratings
Reviews
(1-5 of 5)Companies can't remove reviews or game the system. Here's why
Currently, Bitbucket Server (formerly Stash) is being used as the primary version control system in my organization. This means it is being used pretty standardly across both operations and development teams. This also means it is allowing multiple teams to collaborate on code as any version control system would within an organization.
- Bitbucket is, as far as things go, good at being a version control system. In look and feel, it's very much like GitHub with regard to structure and browsing code.
- Bitbucket Server has quite a few integrations out of the box that make it pretty quick and not very painful to integrate other systems (Jenkins for example).
- When restoring from backup, Bitbucket Server does not re-enable plugins that were once enabled. This means anytime you rebuild you are left to either go with enabling all of them or disabling all of them and waiting for other downstream systems to break.
- Permissions on repositories and projects are not very straight forward. From a user interface perspective, it's a little unclear the first time how to lock down things like pushing to master for some but not others, how to all others to merge pull requests (thus pushing to master) as long as it's not their own change, etc.
- Reliability is a real problem with Bitbucket Server. Sometimes, for no apparent reason, it will just decide to stop working and require a full restart of the application (which takes a fair bit of time). Being the primary version control system, this means there are quite a few people unable to complete their work while these issues are resolved.
- N/A
- GitHub, Gitlab, Azure DevOps (formerly VSTS) and Azure DevOps Server (formerly Team Foundation Server)
If you are selecting a product to use and you are not currently using version control, it may be in your best interest to choose another tool. Bitbucket Server is not as feature rich and doesn't feel as mature as some other platforms and arguably, with the lost production from it's reliability issues, there isn't much money to be saved from using Bitbucket over something like Gitlab or GitHub. The user interface of the other tools is much easier to interact with and from a user management perspective it is much easier to get fine grained controls on projects/repositories. Additionally, the other tools have an easier time with integration of CI/CD solutions (GitHub Actions and Gitlab pipelines). Bamboo doesn't feel as useful and user friendly as the other two options.
Developer
Operations
Engineering
Operations
Engineering
3
Miracle workers! (kidding)
System Administration Skills a must!
Familiarity with how a VCS system should run
System Administration Skills a must!
Familiarity with how a VCS system should run
- Version control system (it's our primary system)
- Integrations with application build pipelines (mostly Jenkins)
April 13, 2017
Stash for GIT
We switched to stash from TFS across whole organization due some limitations that we facing at TFS, especially on branching. On top of that, my company is using some of Atlassian's other products as well such as Bamboo, JIRA and Confluence, and we wanted to integrate the process of CD/CI seamlessly so Stash is an ideal choice.
- Able to resolve the high priority problem quickly with right branch strategy.
March 27, 2017
Functional but Free of Fun Extras
Our entire organization uses Stash for all code repositories. We store code in repositories specific to applications. Each department has control over a section of repositories. Some applications are spread across multiple repositories when they have deep collections of dependencies or scripts. We also use the pull requests system of stash for all code changes. Most if not all departments require two approvers for every pull request to be merged.
- Integrations with HipChat are solid, informative, and easy.
- Pull requests are easy to comment on, discuss, approve, deny, and merge. It has a very intuitive workflow.
- It's difficult to create flexible pull requests that might need to be approved by 4 people and others by only 1 person. All pull requests require the same number of approvers
- Maneuvering through the git-components of Stash to look at particular branches, diff branches, or view tags can be difficult, tedious, or impossible. Direct support for some more advanced git actions would be appreciated.
- There is no readme concept (like in GitHub) for a repository.
- In positive form, having Stash over not having it at all has provided us with a superior repository system over trying to push to some local server instance and manage branches/merging from our local machines.
- There are no real negatives to using Stash, its only problem is that there are competitors out there that can offer additional features.
Stash was selected before I was at the company, but we're looking at these alternatives and actively considering switching. Stash seems to have all the necessary features we need to make it work, but it doesn't have any bells and whistles or extra special features that we can use to create more advanced integrations with other products like Jenkins or Amazon Web Services.
No
- Price
- Product Reputation
- Existing Relationship with the Vendor
March 21, 2017
STASH and JIRA - Atlassian's must have
Stash is being used to handle pull requests from JIRA issues into our development and production branches. Also, it is configured to run builds for java applications whenever a pull request is accepted into development branch. It has a nice and easy UI. Also used to create branches directly if not attached to a JIRA issue. Its integration with JIRA is the big plus of this product.
- Integration with JIRA
- Easy to use
- Review and accept code changes
- More free plugins
- Hooks examples
- Better control of branches parents
- Higher productivity
- Higher understading of problems
- Higher liability of code changes
November 11, 2016
Atlassian Stash - Emergence of User Friendly Version Control
Stash is used primarily for version control of different modules of codes within various teams at Fidelity Investments. Ours is a cross functional team geographically located in different time zones. The development team works on a piece on code, pushes the code onto the Stash server, which is then pulled by the testing team for review. Upon final approval, the release engineering team pulls the code from server and moves across various environments. Continuous availability of correct version of code is big business problem that gets solved because of the usage of Stash.
- Projects & Permissions - Stash keeps you and your developers productive by providing a way to structure your repositories and manage permissions via a simple, yet powerful user interface. Stash is very easy to use, manage & administer.
- Essentially Stash gives two versions of interfaces to work with.
- Stash Repository hosted on a server.
- Atlassian SourceTree.
- Atlassian Sourcetree is a tool to work with a code in stash. The two 'web' and 'desktop' versions make working with code user friendly, intuitive and comprehensive.
- Connectivity to JIRA - Stash keeps track of all issues associated with commits. Users can use Stash to quickly see all issues associated with a commit, or use the Source tab on JIRA issues for an aggregate view of all the code changes that are related to a specific JIRA issue. With this information available, your development team saves time when tracking particular bug fixes or improvements.
- I feel Stash should allow direct download of the entire folder containing various files of code. It is cumbersome to go inside a folder to download an sql file and then come back to the folder to download another.
- With respect to security password syncing between Stash & Sourcetree, there should be a mechanism of automatic syncing of passwords. In urgency if I need to download a piece of code and pull doesn't work simply because the authentication fails.
- Sometimes Stash gives problems while pulling files with long file names. I feel this can be addressed and there should not be any such restriction.
- Stash has certainly improved the productivity of the team. We no longer have to use Shared Drive on network which is prone to hacks and errors to manage our code.
- During the process of releases, the release engineering team can pull the latest and approved code from Stash and need not be dependent upon the availability of the developers during their non availability. It improves productivity and fastens the ETA for requests.
- We have stayed on course for project deadlines since introduction of Stash and helps us achieve the goals of timely completion of projects.